Release 10.1A: OpenEdge Data Management:
DataServer for ODBC

Security

Using the OpenEdge DataServer for ODBC involves following the security guidelines required by both the OpenEdge database and the ODBC data source. By default, OpenEdge allows unrestricted access to data sources, so at minimum, you should follow the guidelines that the data source requires for your applications.

OpenEdge security

The OpenEdge database management system has no minimum security requirements. You can, however, impose security features on any OpenEdge database or schema holder. There are four levels of application security that you can impose:

Database-connection security.
Schema security.
Compile-time security.
Run-time security.

For more information about compile-time and run-time security, see the OpenEdge Deployment: Managing 4GL Applications. For general information about OpenEdge security, see OpenEdge Getting Started: Security.

ODBC data-source security

As noted previously, you should follow the security guidelines that your ODBC data source has established for your applications. Some ODBC data sources require that all users supply a valid login name and password to access it. In addition, ODBC data sources often provide security that controls access to data sources and objects within data sources. Data-source access security typically has four levels—system administrator, database owner, database object owner, and public:

System administrators can grant or revoke permissions to other users to create or own a wide type of objects; for example, databases.
Database owners can grant other users permission to access or modify a database or its objects.
A user can be the owner of objects in a database owned by another user.
Public database objects can be accessed by any users without restriction.

For more information on database security, see the documentation for your data source.

Note: There are specific security requirements for accessing data with the DataServer that relate to creating a schema holder. For details, see the "Creating a schema holder" section.